the required `growpart` and `xfs_growfs` commands
are run as a systemd service which is part of the
self-sufficient bundle

for microshift preset this is handled by crc like
before

since the dnsmasq config is added by a systemd service in the
self-sufficient bundle we can remove the code from crc

this removes code adding the pull-secret to the
cluster using `oc`, instead it copies the  pull
secret file to /opt/crc/crc-pullsecret which is
then used by a systemd service in the bundle to
add the pull secret to the cluster for both the
openshift and microshift presets

this copies the generated kubeadmin and developer
user passwords to `/opt/crc/` which is then  used
by a systemd service and modifies the needed  ocp
resources

this is done via a systemd service on the bundle
which automatically starts the routes controller
pod after the cluster is started

this is done by a systemd service in the bundle
so the code on crc can be removed

this removes the code patching the configmap admin-kubeconfig-client-ca
to use the custom CA, instead it copies the generated CA to '/opt/crc/'
which is then used by a systemd service to created the required  secret
and updates the configmap